Emergency services delivery

ABSTRACT

A cell broadcast emergency services delivery mechanism for vehicular Internet of Things (IoT) communication is provided. A method can comprise receiving, from a federal emergency management agency device, first data representing federal management emergency event data, aggregating second data representing an emergency event associated with a vehicle with the first data to form third data, based on the emergency event data and the third data, determining a commonality between the first data and the second data, in response to determining the commonality between the first data and the second data, generating metadata, and broadcasting the metadata to the vehicle.

RELATED APPLICATION

The subject patent application is a continuation of, and claims priorityto, U.S. patent application Ser. No. 15/485,826, filed Apr. 12, 2017,and entitled “EMERGENCY SERVICES DELIVERY,” the entirety of whichapplication is hereby incorporated by reference herein.

TECHNICAL FIELD

The disclosed subject matter relates to providing cell broadcastemergency services delivery for vehicular Internet of Things (IoT)communication.

BACKGROUND

The wireless emergency alert (WEA) network architecture is designed andimplemented to support emergency messages of limited length (e.g., up to82 octets (single page)) on 2G GSM, 3G UMTS, and long term evolution(LTE) radio network environments. The current network architecture wasdesigned with a traffic model assumption of four alerts/minute. Thecurrent wireless emergency alert network architecture therefore is notcapable of handling emergency broadcast messages of larger sizes withcontent that requires higher throughput rates.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is an illustration of a system for cell broadcast emergencyservices delivery for vehicle Internet of Things (IoT) communication, inaccordance with aspects of the subject disclosure.

FIG. 2 is a further depiction of a further system for cell broadcastemergency services delivery for vehicle Internet of Things (IoT)communication, in accordance with aspects of the subject disclosure.

FIG. 3 provides illustration of an additional system for cell broadcastemergency services delivery for vehicle Internet of Things (IoT)communication, in accordance with aspects of the subject disclosure.

FIG. 4 provides illustration of another system for cell broadcastemergency services delivery for vehicle Internet of Things (IoT)communication, in accordance with aspects of the subject disclosure.

FIG. 5 provides depiction of a further system for cell broadcastemergency services delivery for vehicle Internet of Things (IoT)communication, in accordance with aspects of the subject disclosure.

FIG. 6 provides additional illustration of a system for cell broadcastemergency services delivery for vehicle Internet of Things (IoT)communication, in accordance with aspects of the subject disclosure

FIG. 7 provides illustration of a flow or method for cell broadcastemergency services delivery for vehicle Internet of Things (IoT)communication, in accordance with aspects of the subject disclosure.

FIG. 8 illustrates another depiction of a flow or method for cellbroadcast emergency services delivery for vehicle Internet of Things(IoT) communication, in accordance with aspects of the subjectdisclosure.

FIG. 9 is a block diagram of an example embodiment of a mobile networkplatform to implement and exploit various features or aspects of thesubject disclosure.

FIG. 10 illustrates a block diagram of a computing system operable toexecute the disclosed systems and methods in accordance with anembodiment.

DETAILED DESCRIPTION

The subject disclosure is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the subject disclosure. It may be evident, however,that the subject disclosure may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form in order to facilitate describing the subjectdisclosure.

It should be realized and appreciated by those of ordinary skill thatthe foregoing non-limiting example application is merely an illustrationof a use of the disclosed and described solution and is provided onlyfor the purposes of exposition. The described and disclosed subjectmatter is therefore not limited to the foregoing example application,but can find applicability in other more generalized circumstances anduse applications.

There are currently discussions in the Federal Communications Commission(FCC) regarding geo targeting granularity, device assisted geo targeting(e.g., user mobile devices determined where it is in relation to definedgeographic coordinates and displays a wireless emergency alert when theuser mobile device in or proximate to the polygon that circumscribes thedefined geographic coordinates), inclusion of Uniform ResourceIdentifiers (URIs) or Uniform Resource Locators (URLs) in the emergencyalert message.

In relation to, and in addition to, the foregoing, there are otherpotential broadcast services that can be leveraged, such as leveragingexisting network infrastructure to support emergency services for nextgeneration of fleet automotive transportation vehicles (includingemergency, public safety, schools, and commercial), commercialbroadcasts, etc. The wireless emergency alert service (formally known asCommercial Mobile Alert Service (CMAS) network architecture was designedand implemented to support emergency messages with limited lengths of upto 82 octets (single page) on 2G GSM, 3G UMTS and LTE radio. The currentwireless emergency alert network architecture does not handle emergencybroadcast messages of larger size at higher rates.

The current wireless emergency alert regulatory service was designedwith a traffic model assumption of 4 alerts/minute. The wirelessemergency alert network infrastructure, in particular radio accessnetwork-based delivery has limited capability as the emergency alertsare broadcast over system information block 12 (SIB12) data structuresin LTE networks. SIB12 data structures have limitations per standardsdefinition and thus are not suitable for large message delivery.

Alternate mobile core network architecture and design solutions need tobe explored to support emergency message delivery with larger size,varying media types (SMS, MMS, images, URLs, file downloads, etc.) andat a higher alerting rate by leveraging existing wireless emergencyalert infrastructure and evolved Multimedia Broadcast Multicast Service(eMBMS) solutions, as well as proposing new enhancements into suchnetworks in the way they can be integrated to efficiently interwork witheach other to deliver the best service experience to the end-user.

The subject application provides a new signaling interface between thecell broadcast center (CBC) and broadcast multicast service center(BMSC) that can provide a suitable trigger for differentiating emergencyand commercial messages broadcast that meets certain pre-defined messagecharacteristics. Such capabilities can be dynamically learned viamapping functions in the CBC and segregating the emergency versuscommercial broadcast requests during alert generation. By leveraging asimple control plane engine that performs integrated Mobility ManagementEntity (MME)/S4-SGSN and Multimedia Broadcast Multicast Service gateway(MBMS-GW) core network functions, the CBC and BMSC can interactefficiently and optimally with the control engine to differentiate andtrigger on-demand session establishment for rapid emergency andcommercial broadcast message alert delivery.

In traditional cellular mobility network architectures developed forbroadcast warning message alert delivery, regulatory and public safetyauthorities have provides a feed for the alert to be propagated into themobility network through the CBC. In long term evolution (LTE) networks,the CBC leverages a SBc interface towards the MME to deliver the warningmessages. The MME then uses S1AP messaging to complete the emergencybroadcasts in the targeted cells.

With the advances in vehicular communications, intelligent networking ofautomotive/fleet, humans, and internet of things (IoT) deviceconnectivity, there is a need for an enhanced emergency broadcastwarning alert delivery network infrastructure. These alerts that can begenerated by a variety of transport vehicles in different forms from agiven location or across multiple geographic locations can be used inturn by the cell broadcast network intelligently as potential warningindications to incoming vehicles to steer such traffic away, to avoidimpending congestion, transport delays, emergency situation handling,efficient human-machine interactions, etc.

The current 3GPP standards based cell broadcast network architecturecannot handle the signaling load generated by massive numbers of devicesin a single cell or across multiple cells in a given coverage area.While the SBc interface can help CBC deliver the warning alert messages(with limited characters, 90 bytes) to MME via the control plane, theCBC in its current design is not equipped to handle and deliver alertswith larger message sizes of a few kilobytes (KB) from commercialproviders on the SBc interface. For example, if a commercial serviceprovider wants to send emergency broadcast alerts to users within atarget geographic area with rich data sets (images, files, coupons,etc.), the control plane delivery method via CBC is not optimal. Such anarchitecture has fundamental limitations in terms of data handling,capacity, scalability, latency and service reliability as it affects allnetwork elements—CBC, MME, RAN, and the way these interwork at thecontrol plane before the final broadcast delivery happens via SIB12 datastructure message over the air. SIB12 data structure based messagedelivery has pre-defined limits and exceeding these limits can result indata fragmentation which in turn can lead to extended emergencybroadcast message delivery times that may not be acceptable. eNodeB(eNB) devices can support limited numbers of simultaneous alertbroadcasts, which can possibly result in throttling of any new oradditional emergency alert broadcast requests.

To overcome the data fragmentation and extend delivery issues associatedwith cell broadcast architecture, the subject disclosure provides adirect signaling interface between the CBC and the BMSC that is utilizedby the CBC to generate traffic event notifications or certificatemanagement and distribution towards a targeted and defined geo-mappedpolygonal area. Such a trigger can be generated by the CBC based onstimulus received from external cell broadcast entities (CBE) that canbe fed to a traffic aggregator for commercial requests or directinterface “1” from each CBE to CBC. The direct interface model helps inconverging emergency and commercial broadcast network architectures, aswell as simplifies the overall broadcast delivery method for any type ofmessage alerts targeted for efficient human, machine interactions.

The disclosed systems and methods, in accordance with an embodiment,provide a machine, system, apparatus, or device comprising: a processor;and a memory that stores executable instructions that, when executed bythe processor, facilitate performance of operations. The operations cancomprise receiving first data representative of an emergency eventassociated with a vehicle, aggregating the first data with second datato form third data, determining, as a function of the emergency eventand the third data, a commonality between the first data and the seconddata; based on the commonality identified between the first data and thesecond data generating metadata; and transmitting the metadata to thevehicle.

Additional operations can include identifying a network device ofnetwork devices situated in a defined geographical area represented by alongitude coordinate and a latitude coordinate, determining a definedperipheral boundary that circumscribes the longitude coordinate and thelatitude coordinate, and identifying the network device (e.g., eNodeBdevices, cell devices, tracking area identifiers (TAIs), etc) within thedefined peripheral boundary.

In relation to the foregoing, the second data can have been receivedfrom a federal emergency management agency device. The first data cancomprise longitude coordinate data associated with a vehicle andlatitude coordinate data also associated with the vehicle. The firstdata can have been received in response to an engine control unitassociated with the vehicle having detected a deceleration, or change invelocity, of the vehicle and/or the first data can have been received inresponse to an engine control unit associated with the vehicle havingdetected a deployment of an bag safety device of the vehicle.

In accordance with a further embodiment, the subject disclosuredescribes a method or process, comprising a series of acts that caninclude: receiving, by a system comprising a processor, first datarepresentative of an emergency event associated with a vehicle,associating, by the system, the first data with second data to formthird data, based on the emergency event data and the third data,determining, by the system, an existence of a commonality between thefirst data and the second data, generating metadata, by the system, as afunction of the existence of the commonality; and sending the metadatato the vehicles in the area of relevance.

Further acts can comprise receiving the second data from federalemergency management agency devices, identifying network devices locatedin defined geographical areas as a function of longitude coordinates andlatitude coordinates, and determining defined peripheral boundaries thatpolygonally surround the longitude coordinates and the latitudecoordinates, wherein the longitude coordinates and the latitudecoordinates are associated with the vehicle and wherein the longitudecoordinates and the latitude coordinates are obtained from globalpositioning satellite system devices.

In accordance with a still further embodiment, the subject disclosuredescribes a machine readable storage medium, a computer readable storagedevice, or non-transitory machine readable media comprising instructionsthat, in response to execution, cause a computing system comprising atleast one processor to perform operations. The operations can include:receiving, from a federal emergency management agency device, first datarepresenting federal management emergency event data, aggregating seconddata representing an emergency event associated with a vehicle with thefirst data to form third data, based on the emergency event data and thethird data, determining a common cross-section between the first dataand the second data, in response to determining the common cross-sectionbetween the first data and the second data, generating metadata, andbroadcasting the metadata to the vehicle.

Further operations can comprise initiating a session establishmentprotocol to establish a session with a network device of network devicesassociated with a radio access network, and as a function of a longitudecoordinate associated with the network device and a latitude coordinateassociated with the network device, determining a defined peripheralboundary that encloses the network device.

Now with reference to the Figures, FIG. 1 illustrates a system 100 thatin accordance with various embodiments provides a system, machine,apparatus, or device for cell broadcast emergency services delivery forvehicular Internet of Things (IoT) communication. System 100, forpurposes of illustration, can be any type of mechanism, machine, device,facility, apparatus, and/or instrument that includes a processor and/oris capable of effective and/or operative communication with a wiredand/or wireless network topology. Mechanisms, machines, apparatuses,devices, facilities, and/or instruments that can comprise system 100 caninclude tablet computing devices, handheld devices, server classcomputing devices, machines, and/or databases, laptop computers,notebook computers, desktop computers, cell phones, smart phones,consumer appliances and/or instrumentation, industrial devices and/orcomponents, hand-held devices, personal digital assistants, multimediaInternet enabled phones, multimedia players, consumer and/or industrialappliances and/or instrumentation associated with automotive vehicles,industrial and/or consumer appliances and/or instrumentation associatedwith aerospace vehicles and/or satellites orbiting in low earth orbit,geosynchronous orbit, and the like.

As illustrated, system 100 can comprise delivery engine 102 that can bein operative communication with processor 104, memory 106, and storage108. Delivery engine 102 can be in communication with processor 104 forfacilitating operation of computer-executable instructions ormachine-executable instructions and/or components by delivery engine102, memory 106, for storing data and/or computer-executableinstructions or machine-executable instructions and/or components, andstorage 108 for providing longer term storage of data and/ormachine-readable instructions and/or computer-readable instructions.Additionally, system 100 can also receive input 110 for use,manipulation, and/or transformation by delivery engine 102 to produceone or more useful, concrete, and tangible results, and/or transform oneor more articles to different states or things. Further, system 100 canalso generate and output the useful, concrete, and tangible resultsand/or the transformed one or more articles as output 112.

In accordance with an embodiment delivery engine 102 can receive, asinput 110, event data from devices that can be associated with vehicles,such as wagons, bicycles, motor vehicles (e.g., motorcycles, cars,trucks, buses, . . . ), railed vehicles (e.g., trains, trams, rollingstock, etc.), watercraft (e.g., ships, boats), aircraft, and/orspacecraft. Typically, the devices associated with vehicles can be incommunication with, for instance, engine control unit (ECU) devices thattypically control engines (e.g., internal combustion engines,aviation/aircraft engines, diesel electric engines, and the like) toensure optimal engine performance. ECU devices typically control enginefunctionality by reading data values from a plurality of sensors, andinterpreting the data values using, for instance, multidimensionalperformance maps (e.g., lookup tables, or other data structures), andadjusting (e.g., through actuators associated with the engine) engineparameters, such as air fuel mixture, ignition timing, idle speed, etc.Other devices that can also be associated with vehicles can includesensors/devices that indicate whether collision avoidance devicesaffiliated, externally and/or internally, with the vehicle have beendeployed. For instance, application of emergency braking; deployment ofbag devices; monitoring of wheel speed indicators (e.g., used to provideindication of icy or rain slicked road conditions, etc.); sensors thatindicate ambient air temperatures and humidity (e.g., inside and outsidethe vehicle); . . . .

In the context of the other devices that can be associated with, orcommunicatively coupled to, vehicles and/or affiliated ECU devices,these devices, like system 100, can be any type of mechanism, machine,device, facility, apparatus, and/or instrument that includes a processorand/or is capable of effective and/or operative communication with awired and/or wireless network topology. Machines, mechanisms,apparatuses, devices, facilities, and/or instruments that can comprisethese other devices that can be associated with, or communicativelycoupled to, vehicles and/or affiliated ECU devices can include tabletcomputing devices, handheld devices, server class computing devicesand/or databases, laptop computers, notebook computers, desktopcomputers, cell phones, smart phones, consumer appliances and/orinstrumentation, industrial devices and/or components, hand-helddevices, personal digital assistants, multimedia Internet enabledphones, multimedia players, consumer and/or industrial appliances and/orinstrumentation associated with automotive vehicles, industrial and/orconsumer appliances and/or instrumentation associated with aerospacevehicles and/or satellites orbiting in low earth orbit, geosynchronousorbit, and the like.

Delivery engine 102, based on, as a function of, or in response toreceiving event data from devices associated with, or coupled to,vehicles, analyzes the event data based on criteria, such asgeographical location information regarding the geographical location(e.g., latitude and longitude data/coordinates, geo-location codes, GPScoordinates) of the vehicle, type of conditions being experienced by thevehicle as indicated by multiple sensors associated with the vehicle.

In accordance with an embodiment, the geographical location informationcan be obtained from a network device (e.g. eNodeB device, access pointdevice, serving cell device, cell broadcast center device, . . . ) withwhich the respective devices associated with, or coupled to, thevehicles are in communication. For example, devices associated with avehicle can be in communication with, and located in the proximity of, anetwork device that is situated at the geographic coordinate: 22° 17′07″ North, 114° 09′ 27″ East (e.g., latitude: 22° 17′ 07″ N, longitude:114° 09′ 27″ E). Accordingly, based on the geographic coordinate dataattributed to the network device, it can be determined that the vehicleis in the vicinity of the geographic coordinate: 22° 17′ 07″ North, 114°09′ 27″ East.

In accordance with an additional embodiment, the geographical locationinformation of the vehicle can be obtained from a space-based radionavigation system, such as the global positioning system (GPS). Thegeographical location information can have been included in the eventdata transmitted and/or communicated by the devices that are in datainterchange with the network device and that are associated with, orcoupled to, the vehicles.

Other information that can comprise event data can include informationsuch as whether emergency breaking has been initiated; whether collisionavoidance measures have been undertaken (e.g., by the driver, orautomatically, in the case of a vehicle capable of sensing itsenvironment and navigating without human input); whether vehicle safetydevices and/or occupant restraint systems have been activated; whetherengine speeds have been gradually reduced from a first non-idle speed toan idle speed, or rapidly reduced from a first non-idle speed to engineshut off within a curtailed definable period of time; whether thevehicle came to a gradual stop/halt or an abrupt stop/halt; and/orweather conditions that the vehicle can currently be experiencing (e.g.,blizzard conditions, freezing rain, torrential rain, hail, sleet, highwind speeds, sun glare, . . . ). Further information that can alsocomprise event data can be information associated with roadimpediments/hazards, such as whether there have been landslides, rockfalls, fallen trees/tree limbs, fallen telephone poles due to high windsor ice events (e.g., freezing rain), downed power lines (transmissionlines), and other impediments/hazards on the road. Additionalinformation that can also comprise event data can include informationassociated with traffic conditions (e.g., traffic accidents, trafficcongestion, traffic slow downs, presence of emergency vehicles),accident events, and other emergency events occurring in the vicinity ofthe geographic coordinate data/geographical location information, etc.

Subsequent to analyzing the event data, delivery engine 102 canaggregate the data based on the analysis and/or one or morecharacteristic associated with the event to form metadata. For instance,delivery engine 102 can aggregate the received events to form metadatabased on at least one of geographical location, time, type of incidentthat has occurred, weather conditions currently being encountered by thevehicle, road impediment/hazards experienced by the vehicle, etc. Forexample, in an embodiment, delivery engine 102 can aggregate thereceived data to form metadata based on a commonality of geographicallocation, time, and/or weather condition experienced by a first vehicleand a plurality of second vehicles that can share the commonality ofgeographical location, time, and/or weather condition experienced. In analternative and/or additional embodiment, delivery engine 102 canaggregate the received event data to form metadata as a function of acommonality of geographical location and/or road impediment/hazardexperienced by first and second vehicles. In an additional and/oralternative embodiment, delivery engine 102 can aggregate the receivedevent data to form metadata based on time and/or type of incident thathas occurred. Additionally, and/or alternatively, delivery engine 102can aggregate the received event data with federal emergency managementagency data that can have been received from a federal emergencymanagement agency device, wherein the federal emergency managementagency device supplies, based on geographical location, federalemergency management agency data representing data such as Amber alertdata, evacuation data (e.g., data associated with the fact that certainareas/zones have been declared evacuation zones due to naturaldisasters, or impending natural disasters, such blizzards, hurricanes,tornadoes, landslides, earthquakes, and the like), road closures (e.g.,due to hazardous material spills, slick road surfaces, heavy fog, and/orearlier traffic accidents caused by, or as consequence of, hazardousmaterial spills, slick road surfaces, heavy fog, . . . ), imposition ofcurfews, and the like. For instance, delivery engine 102 can aggregate,correlate, collate, and collect the received event data based on the acommonality of geographical location of vehicles and federal emergencymanagement agency data.

Delivery engine 102 can thereafter analyzes the metadata based on, forexample, one or more of geographical location, time, type of incidentthat has occurred, weather conditions currently being encountered by thevehicle, road impediment/hazards experienced by the vehicle, federalemergency management agency data in the context of Amber alert data,data associated evacuations relating to natural disasters/impendingnatural disasters, road closures/impending road closures, and the liketo generate broadcast data. Broadcast data can, for example, begenerated by delivery engine 102 based on time data, geographicallocation data, and federal emergency management agency data, so thatwhen, for instance, an Amber alert is initiated, an emergency messagecan be selectively broadcast to all vehicles in a defined or specificgeographical area and geographically surrounding areas. In this manner,broadcast data can be directed, by delivery engine 102, to only thosedefined and/or specified areas within which there is an immediateurgency, or within which the broadcast data will have immediate impactand/or effect.

In regard to the foregoing analysis of metadata based on, for instance,geographical location, time, type of instance, weather conditions roadimpediment/hazards, delivery engine 102, as a function of geographicalcoordinate data (e.g., geographical location) can determine atransmission area that can bound the geographical coordinate data. Forinstance, delivery engine 102 can determine that the transmission areabounding the geographical coordinate area should encompass an area ofπr², where r is a radius measured using relevant coordinate data.

Delivery engine 102, in response to having generated broadcast data andusing one or more establishment protocols, can initiate and establishcommunications sessions with a plurality of devices associated with aradio access network (e.g., universal mobile telecommunications system(UTMS) terrestrial radio access network (UTRAN) and/or evolved UTMSterrestrial radio access network (EUTRAN)). Devices associated with theradio access network with which delivery engine 102 can initiate andestablish a session can include eNodeB devices, access point devices,base station devices, home eNodeB devices, femto cell devices, Pico celldevices, and the like. Each of the plurality of devices associated withthe radio access network, in response to receiving a request to initiateand establish a communication session with delivery engine 102, canrespond with acknowledgment data that notifies that at least one of theplurality of devices is ready to commence data interchange with deliveryengine 102 (e.g., acknowledgement that one or more of the plurality ofdevices is in a state of readiness to communicate with delivery engine102); and that the a communication session has been established.

Thereafter, delivery engine 102, on receiving an acknowledgment from oneor more of the plurality of devices that the one or more of theplurality of devices are in a state of readiness to communicate withdelivery engine 102, can send the broadcast message to the one or moreof the plurality devices (e.g., eNodeB devices, access point devices,base station devices, home eNodeB devices, femto cell devices, Pico celldevices, and the like). It will be noted at this juncture that the oneor more of the plurality of devices will have been typicallyselected/identified by delivery engine 102 based on, as a function of,or in response to determination of a pertinent transmission area(s). Forinstance, in accordance with an aspect, the transmission area(s) can bedetermined by delivery engine 102 based on an area(s) immediatelysurrounding and/or contiguous to system 100. In accordance with anadditional and/or alternative aspect, the transmission area(s) can bedetermined by delivery engine 102 based on a contiguous area(s) thatsurround the geographic coordinate data supplied in event data receivedfrom devices associated with vehicles. In accordance with yet a furtheraspect, the transmission area(s) can be determined by delivery engine102 based on a polygonally adjoining area(s) that bound or surrounds thegeographic coordinate data that can have been supplied and included inthe event data. The neighboring, contiguous, adjacent, abutting area(s)identified and/or determined by delivery engine 102 can include one ormore other systems that can have similar functionalities to thosedescribed herein in regard to system 100. As such system 100, and theone or more other systems with facilities and/or functionalities similarto those described from system 100, can collaborate with each other inbroadcasting the broadcast message to the plurality of devicesassociated with a radio access network, such as eNodeB devices, accesspoint devices, base station devices, home eNodeB devices, femto celldevices, Pico cell devices, and the like. The plurality of devicesassociated with the radio access network can thereafter broadcast thebroadcast message to devices that are in communication with theplurality of devices. For example, where delivery engine 102 sends thebroadcast message to an eNodeB device of eNodeB devices in atransmission area defined by delivery engine 102, the eNodeB device canforward the broadcast message to a user equipment device associated witha first vehicle situated in the broadcasting area of the eNodeB deviceand in proximity to the geographic coordinate data that was earlierreceived by delivery engine 102 as event data, or determined by deliveryengine 102 as a function of the geographic coordinate data included inthe event data.

FIG. 2 depicts a further illustration of a system 100, now illustratedas system 200, for cell broadcast emergency services delivery forvehicular Internet of Things (IoT) communication. As illustrated, system200 can include traffic optimization manager 202 that in collaborationwith delivery engine 102, processor 104, memory 106, and/or storage 108can receive event data from devices associated with vehicles. The eventdata can be received from devices associated with vehicles and cancomprise data related to engine functionality, data representing whetheror not collision avoidance devices have been deployed, data related towheel speed indicators, or data indicative of ambient at temperaturesand humidity, both inside and outside a vehicle. Additionally, the eventdata can include geographic coordinate data, geo-location codes, or dataobtained from space-based radio navigation systems.

Traffic optimization manager 202 can aggregate the received event databased on commonalities of criteria associated with the received eventdata. For instance, traffic optimization manager 202 can aggregate,sort, correlate, and/or collate the received event data as a function ofgeographic coordinate data, geo-location code, and/or data obtained fromspace-based radio navigation systems. Further, traffic optimizationmanager 202 can aggregate, sort, correlate, and/or collate the receivedevent data based on the type of data such as data representing enginefunctionality, data representing whether or not collision avoidancedevices have been deployed, data related to wheel speed indicators,and/or data indicative of environmental conditions inside and outside avehicle. Additionally, traffic optimization manager 202 can aggregate,sort, correlate, and/or collate event data with federal emergencymanagement agency data that can have been received by trafficoptimization manager 202 from one or more federal emergency managementagency devices. The aggregated, sorted, correlated, and/or collated datacan form metadata.

As has been noted earlier, federal emergency management data can includedata related to Amber alerts, evacuation data, road closure information,imposition of curfews, and the like. Thus, traffic optimization manager202, in addition to aggregating the received event data as a function ofcommonalities associated with geographic coordinate data, geo-locationcode, and/or data obtained from space-based radio navigation systems,type of data representing one or more of engine functionality, whetheror not collision avoidance devices have been deployed, wheel speedindicators information, and/or data indicative and environmentalconditions experienced within and outside the vehicle, can alsoaggregate, correlate, and/or collate the data as a function ofcommonalities associated with federal emergency management data.

Traffic optimization manager 202 can analyze the metadata as a functionof second commonalities of criteria representative, for example, ofgeographical coordinates associated with the metadata. Trafficoptimization manager 102 can perform such analysis using, for example,artificial intelligence functionalities associated with delivery engine102. Such artificial intelligence functionalities can include usingclassifiers that map an input attribute vector, x=(x1, x2, x3, x4, xn),to a confidence that the input belongs to a class, that is,f(x)=confidence(class). Such classification can employ a probabilisticand/or statistical-based analysis (e.g., factoring into the analysisutilities and costs) to infer an action that can be automaticallyperformed.

A support vector machine is an example of a classifier that can beemployed. The support vector machine can operate by finding ahypersurface in the space of possible inputs, which the hypersurfaceattempts to split triggering criteria from non-triggering events.Intuitively, this makes a classification correct for testing data thatis near, but not identical to training data. Other directed andundirected model classification approaches can include, for example,naïve Bayes, Bayesian networks, decision trees, neural networks, fuzzylogic models, and probabilistic classification models providingdifferent patterns of independence can be employed. Classification asused herein also may be inclusive of statistical regression that isutilized to develop models of priority.

Additionally, traffic optimization manager 202, as a function ofgeographic coordinate data included in the metadata can determinepertinent transmission area(s) for broadcast of broadcast data. Forinstance, in accordance with an aspect, the transmission area(s) can bedetermined based on an area(s) immediately surrounding and/or contiguousto system 200. In accordance with additional and/or alternativeembodiments, the transmission area(s) can be determined as a function ofcontiguities related to area(s) that can surround the geographiccoordinate data included in event data received from devices associatedwith vehicles. In accordance with yet a further aspect, the transmissionarea(s) can be determined as functions polygonally adjacent area(s) thatbound or surrounds the geographic coordinate data that can have beensupplied and included in earlier supplied event data and compiled, bytraffic optimization manage 202, as metadata. Neighboring, contiguous,adjacent, abutting area(s) can include one or more other systems thatcan have similar functionalities to those described herein in regard tosystem 100. System 100, and the one or more other collaborating systemscan transmit broadcast messages to a plurality of devices associatedwith a radio access network, such as eNodeB devices, access pointdevices, base station devices, home eNodeB devices, femto cell devices,Pico cell devices, and the like. The plurality of devices associatedwith the radio access network can thereafter broadcast the broadcastmessage to devices that are in communication with the plurality ofdevices.

FIG. 3 illustrates a further depiction of system 100, now illustrated assystem 300, for cell broadcast emergency services delivery for vehicleInternet of Things (IoT) communication. As depicted, system 300 caninclude cell broadcast center 302, that in collaboration with trafficoptimization manager 202, delivery engine 102, processor, 104, memory106, and/or storage 108 can receive data representing at leastgeographic coordinate/geolocation code data and/or event metadata fromtraffic optimization manager 202 and as a function of the geographiccoordinate/geolocation code data determines an area in which an event isoccurring (or has already occurred) that affects at least one vehicle atthe geographic coordinate/geolocation code data point or in theproximity of the geographic coordinate/geolocation code data point.

Cell broadcast center 302 can determine the affected area based on, oras a function of, geographic coordinate/geolocation code data and eventmetadata. For example, cell broadcast center 302 can identify anaffected area as a function of a quantum of events (or an aggregation ofevents) relating to, for instance, a traffic slowdown (bottleneck). Forinstance, a traffic bottleneck/slowdown can be indicated by a plethoraof vehicle within proximity of geographic coordinate/geolocation codedata point(s) reporting application of emergency braking at a nearcontemporaneity of time).

Additionally, cell broadcast center 302 can determine an affected areaas a function of input received from one or more federal emergencymanagement agency devices. For instance, in response to receiving datarepresenting federal emergency management agency data, such as Amberalerts, evacuation directives, hazardous condition events, impedingweather warnings, . . . , cell broadcast center 302 can identify ageographic area to which the federal emergency management agency datapertains and into which the federal emergency management agency datashould be broadcast. As will be appreciated, the federal emergencymanagement agency data can include geographical location data that thecell broadcast center 302 can resolve to ascertain the appropriatelocation into which a broadcast message should be broadcast.

Further, cell broadcast center 302 can also determine whether receiveddata, for instance, federal emergency management agency data is dataheavy. Cell broadcast center 302 can determine whether received data isdata heavy based at least in part on whether the received data comprisestext data and/or uniform resource identifier (URI) data or uniformresource location (URL) data. In instances, where cell broadcast center302 identifies that receive data comprises text data and/or uniformresource identifier data or uniform resource location data, cellbroadcast center 302 can steer such received data to broadcast multicastservice center 402. In instances where cell broadcast center 302identifies the received data as comprising text data, cell broadcastcenter 302 can direct such received data to multimedia broadcast gateway602.

FIG. 4 provides additional depiction of system 100, now illustrated assystem 400, for cell broadcast emergency services delivery for vehicleInternet of Things (IoT) communication. System 400 can include broadcastmulticast service center 402, that in collaboration with cell broadcastcenter 302, traffic optimization manager 202, delivery engine 102,processor, 104, memory 106, and/or storage 108, for example, can receiveinput from cell broadcast center 302 representing affected areas tofurther identify and determine devices associated with the radio accessnetwork (e.g., devices associated with the universal mobiletelecommunications system (UTMS) terrestrial radio access network(UTRAN) and/or evolved UTMS terrestrial radio access network (EUTRAN))that are most proximate to the geographic coordinate/geolocation codedata within the broadcast area identified by cell broadcast center 302.

Further, broadcast multicast service center 402 can determine a definedduration that an alert/broadcast message should be broadcast by thedevices associated with the radio access network and a number of timeswithin the defined duration that the alert/broadcast message should berepeated. In accordance with an embodiment, the duration and the numberof times that an alert/broadcast message can be set so that thealert/broadcast message is broadcast for a duration of two hours and thenumber of times within the duration the alert/broadcast message repeatedcan be set for four times in each hour. In accordance with an additionalor alternative embodiment, the duration can be set to be one hour andthe number of times within the hour that the alert/broadcast message isto be repeated can be set to every five minutes within the duration.

Broadcast multicast service center 402 can also initiate establishmentprocedures/protocols to establish sessions with devices associated withthe radio access network, wherein the devices associated with the radioaccess network can include eNodeB devices, access point devices, Picocell devices, femto cell devices, and the like.

FIG. 5 provides further illustration of system 100, now depicted assystem 500, for cell broadcast emergency services delivery for vehicleInternet of Things (IoT) communication. System 500 includesserving/packet data network gateway 502, in conjunction with broadcastmulticast service center 402, cell broadcast center 302, trafficoptimization manager 202, delivery engine 102, processor 104, memory106, and/or storage 108, performs and provides an interconnectionbetween devices associated with the radio access network (e.g., eNodeBdevices, access point devices, Home eNodeB devices (e.g., HeNB devices),Pico cell devices, femto cell devices, etc.) and user equipment devicesthat can be associated with, or affiliated with vehicles. Serving/packetdata network gateway 502 routes and forwards data packets betweendevices associated with the radio access network and user equipmentdevices affiliated/associated with vehicles over the control planeand/or the user plane.

FIG. 6 depicts an additional illustration of system 100, now depicted assystem 600, for cell broadcast emergency services delivery for vehicleInternet of Things (IoT) communication. System 600 includes multimediabroadcast multicast gateway 600, in collaboration with serving/packetdata network gateway 502, broadcast multicast service center 402, cellbroadcast center 302, traffic optimization manager 202, delivery engine102, processor 104, memory 106, and/or storage 108, provides devicesassociated with the radio access network with multicast related data,such multicast related data can be considered “data heavy” (e.g., richdata sets that in addition to text also comprises URL or URI data, imagedata, file data, short message service (SMS) data, multimedia messagingservice (MMS) data, commercial coupon data, such that the data isgreater than 90 bytes that is the current limit in regard to warningalert messages).

The foregoing functionalities and facilities between trafficoptimization manager 202, cell broadcast center 302, broadcast multicastservice center 402, and serving/packet data network gateway 502, andmultimedia broadcast multicast gateway 602 can be performed over one ormore interfaces including: SGi interfaces that can extend betweenbroadcast multicast service center 402 and serving/packet data networkgateway 502; S4 interfaces that can extend between serving/packet datanetwork gateway 502 and multimedia broadcast multicast gateway 602; SBcinterfaces that can extend between cell broadcast center 302 andmultimedia and broadcast multicast gateway 602; and SGmb interfaces(interfaces used for control plane message exchange between broadcastmulticast service center 402 and multimedia broadcast multicast gateway602) and SGimb interfaces (interfaces utilized for user plane/data planeexchange between multimedia broadcast multicast gateway 602 andbroadcast multicast service center 402) that can extend betweenmultimedia broadcast multicast gateway 602 and broadcast multicastservice center 402.

In view of the example system(s) described above, example method(s) thatcan be implemented in accordance with the disclosed subject matter canbe better appreciated with reference to flowchart in FIGS. 7-8. Forpurposes of simplicity of explanation, example method disclosed hereinis presented and described as a series of acts; however, it is to beunderstood and appreciated that the disclosure is not limited by theorder of acts, as some acts may occur in different orders and/orconcurrently with other acts from that shown and described herein. Forexample, one or more example methods disclosed herein couldalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, interaction diagram(s) mayrepresent methods in accordance with the disclosed subject matter whendisparate entities enact disparate portions of the methods. Furthermore,not all illustrated acts may be required to implement a describedexample method in accordance with the subject specification. Furtheryet, the disclosed example method can be implemented in combination withone or more other methods, to accomplish one or more aspects hereindescribed. It should be further appreciated that the example methoddisclosed throughout the subject specification are capable of beingstored on an article of manufacture (e.g., a computer-readable medium)to allow transporting and transferring such methods to computers forexecution, and thus implementation, by a processor or for storage in amemory.

FIG. 7 illustrates a method 700 for cell broadcast emergency servicesdelivery for vehicle Internet of Things (IoT) communication. Method 700can commence at 702 wherein emergency event data from devices associatedwith a vehicle can be received. At 704 the emergency event data can beanalyzed based on groups of criteria, and based on the analysis theemergency event data can be aggregated to form aggregated metadata. At706 the aggregated metadata can then be further analyzed to producebroadcast data. At 708, in response to the production of broadcast data,a session with a plurality of radio access network devices associatedwith a radio access network can be established. At 710 acknowledgmentdata representative of an indication that a session has been establishedwith a plurality of radio access network devices associated with theradio access network can be received. At 712 based on geographic datadetermined as a function of the aggregated metadata, broadcast datarepresenting at least emergency data can be selectively sent to theplurality of devices. At 714 in response to receiving the broadcast dataeach of the plurality of radio access network devices can send thebroadcast data to a user equipment device associated with the vehicle.

FIG. 8 illustrates a method 800 for cell broadcast emergency servicesdelivery for vehicle Internet of Things (IoT) communication. Method 800can commence at 802 where event data from devices associated withvehicles can be received. At 804 the event data can be aggregated basedon first commonalities of criteria associated with the event data toform aggregated event data. At 806 the aggregated event data can beanalyzed as a function of second commonalities of criteriarepresentative of, for example, geographic coordinate data associatedwith the event data. At 808, as a function of the geographic coordinatedata, a defined area that polygonally bounds or circumscribes thegeographic coordinate data within which the first commonalities ofcriteria occurred can be determined.

FIG. 9 presents an example embodiment 900 of a mobile network platform910 that can implement and exploit one or more aspects of the disclosedsubject matter described herein. Generally, wireless network platform910 can include components, e.g., nodes, gateways, interfaces, servers,or disparate platforms, that facilitate both packet-switched (PS) (e.g.,internet protocol (IP), frame relay, asynchronous transfer mode (ATM))and circuit-switched (CS) traffic (e.g., voice and data), as well ascontrol generation for networked wireless telecommunication. As anon-limiting example, wireless network platform 910 can be included intelecommunications carrier networks, and can be considered carrier-sidecomponents as discussed elsewhere herein. Mobile network platform 910includes CS gateway node(s) 912 which can interface CS traffic receivedfrom legacy networks like telephony network(s) 940 (e.g., publicswitched telephone network (PSTN), or public land mobile network (PLMN))or a signaling system #7 (SS7) network 970. Circuit switched gatewaynode(s) 912 can authorize and authenticate traffic (e.g., voice) arisingfrom such networks. Additionally, CS gateway node(s) 912 can accessmobility, or roaming, data generated through SS7 network 970; forinstance, mobility data stored in a visited location register (VLR),which can reside in memory 930. Moreover, CS gateway node(s) 912interfaces CS-based traffic and signaling and PS gateway node(s) 918. Asan example, in a 3GPP UMTS network, CS gateway node(s) 912 can berealized at least in part in gateway GPRS support node(s) (GGSN). Itshould be appreciated that functionality and specific operation of CSgateway node(s) 912, PS gateway node(s) 918, and serving node(s) 916, isprovided and dictated by radio technology(ies) utilized by mobilenetwork platform 910 for telecommunication.

In addition to receiving and processing CS-switched traffic andsignaling, PS gateway node(s) 918 can authorize and authenticatePS-based data sessions with served mobile devices. Data sessions caninclude traffic, or content(s), exchanged with networks external to thewireless network platform 910, like wide area network(s) (WANs) 950,enterprise network(s) 970, and service network(s) 980, which can beembodied in local area network(s) (LANs), can also be interfaced withmobile network platform 910 through PS gateway node(s) 918. It is to benoted that WANs 950 and enterprise network(s) 960 can embody, at leastin part, a service network(s) like IP multimedia subsystem (IMS). Basedon radio technology layer(s) available in technology resource(s) 917,packet-switched gateway node(s) 918 can generate packet data protocolcontexts when a data session is established; other data structures thatfacilitate routing of packetized data also can be generated. To thatend, in an aspect, PS gateway node(s) 918 can include a tunnel interface(e.g., tunnel termination gateway (TTG) in 3GPP UMTS network(s) (notshown)) which can facilitate packetized communication with disparatewireless network(s), such as Wi-Fi networks.

In embodiment 900, wireless network platform 910 also includes servingnode(s) 916 that, based upon available radio technology layer(s) withintechnology resource(s) 917, convey the various packetized flows of datastreams received through PS gateway node(s) 918. It is to be noted thatfor technology resource(s) 917 that rely primarily on CS communication,server node(s) can deliver traffic without reliance on PS gatewaynode(s) 918; for example, server node(s) can embody at least in part amobile switching center. As an example, in a 3GPP UMTS network, servingnode(s) 916 can be embodied in serving GPRS support node(s) (SGSN).

For radio technologies that exploit packetized communication, server(s)914 in wireless network platform 910 can execute numerous applicationsthat can generate multiple disparate packetized data streams or flows,and manage (e.g., schedule, queue, format . . . ) such flows. Suchapplication(s) can include add-on features to standard services (forexample, provisioning, billing, customer support . . . ) provided bywireless network platform 910. Data streams (e.g., content(s) that arepart of a voice call or data session) can be conveyed to PS gatewaynode(s) 918 for authorization/authentication and initiation of a datasession, and to serving node(s) 916 for communication thereafter. Inaddition to application server, server(s) 914 can include utilityserver(s), a utility server can include a provisioning server, anoperations and maintenance server, a security server that can implementat least in part a certificate authority and firewalls as well as othersecurity mechanisms, and the like. In an aspect, security server(s)secure communication served through wireless network platform 910 toensure network's operation and data integrity in addition toauthorization and authentication procedures that CS gateway node(s) 912and PS gateway node(s) 918 can enact. Moreover, provisioning server(s)can provision services from external network(s) like networks operatedby a disparate service provider; for instance, WAN 950 or GlobalPositioning System (GPS) network(s) (not shown). Provisioning server(s)can also provision coverage through networks associated to wirelessnetwork platform 910 (e.g., deployed and operated by the same serviceprovider), such as femto-cell network(s) (not shown) that enhancewireless service coverage within indoor confined spaces and offloadradio access network resources in order to enhance subscriber serviceexperience within a home or business environment by way of UE 975.

It is to be noted that server(s) 914 can include one or more processorsconfigured to confer at least in part the functionality of macro networkplatform 910. To that end, the one or more processor can execute codeinstructions stored in memory 930, for example. It is should beappreciated that server(s) 914 can include a content manager 915, whichoperates in substantially the same manner as described hereinbefore.

In example embodiment 900, memory 930 can store information related tooperation of wireless network platform 910. Other operationalinformation can include provisioning information of mobile devicesserved through wireless platform network 910, subscriber databases;application intelligence, pricing schemes, e.g., promotional rates,flat-rate programs, couponing campaigns; technical specification(s)consistent with telecommunication protocols for operation of disparateradio, or wireless, technology layers; and so forth. Memory 930 can alsostore information from at least one of telephony network(s) 940, WAN950, enterprise network(s) 960, or SS7 network 970. In an aspect, memory930 can be, for example, accessed as part of a data store component oras a remotely connected memory store.

In order to provide a context for the various aspects of the disclosedsubject matter, FIG. 10, and the following discussion, are intended toprovide a brief, general description of a suitable environment in whichthe various aspects of the disclosed subject matter can be implemented.While the subject matter has been described above in the general contextof computer-executable instructions of a computer program that runs on acomputer and/or computers, those skilled in the art will recognize thatthe disclosed subject matter also can be implemented in combination withother program modules. Generally, program modules include routines,programs, components, data structures, etc. that perform particulartasks and/or implement particular abstract data types.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory, by way of illustration, and not limitation, volatilememory 1020 (see below), non-volatile memory 1022 (see below), diskstorage 1024 (see below), and memory storage 1046 (see below). Further,nonvolatile memory can be included in read only memory (ROM),programmable ROM (PROM), electrically programmable ROM (EPROM),electrically erasable ROM (EEPROM), or flash memory. Volatile memory caninclude random access memory (RAM), which acts as external cache memory.By way of illustration and not limitation, RAM is available in manyforms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronousDRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM(ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM).Additionally, the disclosed memory components of systems or methodsherein are intended to comprise, without being limited to comprising,these and any other suitable types of memory.

Moreover, it will be noted that the disclosed subject matter can bepracticed with other computer system configurations, includingsingle-processor or multiprocessor computer systems, mini-computingdevices, mainframe computers, as well as personal computers, hand-heldcomputing devices (e.g., PDA, phone, watch, tablet computers, netbookcomputers, . . . ), microprocessor-based or programmable consumer orindustrial electronics, and the like. The illustrated aspects can alsobe practiced in distributed computing environments where tasks areperformed by remote processing devices that are linked through acommunications network; however, some if not all aspects of the subjectdisclosure can be practiced on stand-alone computers. In a distributedcomputing environment, program modules can be located in both local andremote memory storage devices.

FIG. 10 illustrates a block diagram of a computing system 1000 operableto execute the disclosed systems and methods in accordance with anembodiment. Computer 1012, which can be, for example, part of thehardware of system 100, includes a processing unit 1014, a system memory1016, and a system bus 1018. System bus 1018 couples system componentsincluding, but not limited to, system memory 1016 to processing unit1014. Processing unit 1014 can be any of various available processors.Dual microprocessors and other multiprocessor architectures also can beemployed as processing unit 1014.

System bus 1018 can be any of several types of bus structure(s)including a memory bus or a memory controller, a peripheral bus or anexternal bus, and/or a local bus using any variety of available busarchitectures including, but not limited to, Industrial StandardArchitecture (ISA), Micro-Channel Architecture (MSA), Extended ISA(EISA), Intelligent Drive Electronics, VESA Local Bus (VLB), PeripheralComponent Interconnect (PCI), Card Bus, Universal Serial Bus (USB),Advanced Graphics Port (AGP), Personal Computer Memory CardInternational Association bus (PCMCIA), Firewire (IEEE 1194), and SmallComputer Systems Interface (SCSI).

System memory 1016 can include volatile memory 1020 and nonvolatilememory 1022. A basic input/output system (BIOS), containing routines totransfer information between elements within computer 1012, such asduring start-up, can be stored in nonvolatile memory 1022. By way ofillustration, and not limitation, nonvolatile memory 1022 can includeROM, PROM, EPROM, EEPROM, or flash memory. Volatile memory 1020 includesRAM, which acts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as SRAM, dynamic RAM(DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM),enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), Rambus direct RAM(RDRAM), direct Rambus dynamic RAM (DRDRAM), and Rambus dynamic RAM(RDRAM).

Computer 1012 can also include removable/non-removable,volatile/non-volatile computer storage media. FIG. 10 illustrates, forexample, disk storage 1024. Disk storage 1024 includes, but is notlimited to, devices like a magnetic disk drive, floppy disk drive, tapedrive, flash memory card, or memory stick. In addition, disk storage1024 can include storage media separately or in combination with otherstorage media including, but not limited to, an optical disk drive suchas a compact disk ROM device (CD-ROM), CD recordable drive (CD-R Drive),CD rewritable drive (CD-RW Drive) or a digital versatile disk ROM drive(DVD-ROM). To facilitate connection of the disk storage devices 1024 tosystem bus 1018, a removable or non-removable interface is typicallyused, such as interface 1026.

Computing devices typically include a variety of media, which caninclude computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disk (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or other tangible media which can beused to store desired information. In this regard, the term “tangible”herein as may be applied to storage, memory or computer-readable media,is to be understood to exclude only propagating intangible signals perse as a modifier and does not relinquish coverage of all standardstorage, memory or computer-readable media that are not only propagatingintangible signals per se. In an aspect, tangible media can includenon-transitory media wherein the term “non-transitory” herein as may beapplied to storage, memory or computer-readable media, is to beunderstood to exclude only propagating transitory signals per se as amodifier and does not relinquish coverage of all standard storage,memory or computer-readable media that are not only propagatingtransitory signals per se. For the avoidance of doubt, the term“computer-readable storage device” is used and defined herein to excludetransitory media. Computer-readable storage media can be accessed by oneor more local or remote computing devices, e.g., via access requests,queries or other data retrieval protocols, for a variety of operationswith respect to the information stored by the medium.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

It can be noted that FIG. 10 describes software that acts as anintermediary between users and computer resources described in suitableoperating environment 1000. Such software includes an operating system1028. Operating system 1028, which can be stored on disk storage 1024,acts to control and allocate resources of computer system 1012. Systemapplications 1030 take advantage of the management of resources byoperating system 1028 through program modules 1032 and program data 1034stored either in system memory 1016 or on disk storage 1024. It is to benoted that the disclosed subject matter can be implemented with variousoperating systems or combinations of operating systems.

A user can enter commands or information into computer 1012 throughinput device(s) 1036. As an example, mobile device and/or portabledevice can include a user interface embodied in a touch sensitivedisplay panel allowing a user to interact with computer 1012. Inputdevices 1036 include, but are not limited to, a pointing device such asa mouse, trackball, stylus, touch pad, keyboard, microphone, joystick,game pad, satellite dish, scanner, TV tuner card, digital camera,digital video camera, web camera, cell phone, smartphone, tabletcomputer, etc. These and other input devices connect to processing unit1014 through system bus 1018 by way of interface port(s) 1038. Interfaceport(s) 1038 include, for example, a serial port, a parallel port, agame port, a universal serial bus (USB), an infrared port, a Bluetoothport, an IP port, or a logical port associated with a wireless service,etc. Output device(s) 1040 use some of the same type of ports as inputdevice(s) 1036.

Thus, for example, a USB port can be used to provide input to computer1012 and to output information from computer 1012 to an output device1040. Output adapter 1042 is provided to illustrate that there are someoutput devices 1040 like monitors, speakers, and printers, among otheroutput devices 1040, which use special adapters. Output adapters 1042include, by way of illustration and not limitation, video and soundcards that provide means of connection between output device 1040 andsystem bus 1018. It should be noted that other devices and/or systems ofdevices provide both input and output capabilities such as remotecomputer(s) 1044.

Computer 1012 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1044. Remote computer(s) 1044 can be a personal computer, a server, arouter, a network PC, cloud storage, cloud service, a workstation, amicroprocessor based appliance, a peer device, or other common networknode and the like, and typically includes many or all of the elementsdescribed relative to computer 1012.

For purposes of brevity, only a memory storage device 1046 isillustrated with remote computer(s) 1044. Remote computer(s) 1044 islogically connected to computer 1012 through a network interface 1048and then physically connected by way of communication connection 1050.Network interface 1048 encompasses wire and/or wireless communicationnetworks such as local-area networks (LAN) and wide-area networks (WAN).LAN technologies include Fiber Distributed Data Interface (FDDI), CopperDistributed Data Interface (CDDI), Ethernet, Token Ring and the like.WAN technologies include, but are not limited to, point-to-point links,circuit-switching networks like Integrated Services Digital Networks(ISDN) and variations thereon, packet switching networks, and DigitalSubscriber Lines (DSL). As noted below, wireless technologies may beused in addition to or in place of the foregoing.

Communication connection(s) 1050 refer(s) to hardware/software employedto connect network interface 1048 to bus 1018. While communicationconnection 1050 is shown for illustrative clarity inside computer 1012,it can also be external to computer 1012. The hardware/software forconnection to network interface 1048 can include, for example, internaland external technologies such as modems, including regular telephonegrade modems, cable modems and DSL modems, ISDN adapters, and Ethernetcards.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments and examples are describedherein for illustrative purposes, various modifications are possiblethat are considered within the scope of such embodiments and examples,as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding Figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor may also be implemented as acombination of computing processing units.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “selector,” “interface,” and the like are intendedto refer to a computer-related entity or an entity related to anoperational apparatus with one or more specific functionalities, whereinthe entity can be either hardware, a combination of hardware andsoftware, software, or software in execution. As an example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration and not limitation, both anapplication running on a server and the server can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media, device readablestorage devices, or machine readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software or firmwareapplication executed by a processor, wherein the processor can beinternal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can include a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Moreover, terms like “user equipment (UE),” “mobile station,” “mobile,”subscriber station,” “subscriber equipment,” “access terminal,”“terminal,” “handset,” and similar terminology, refer to a wirelessdevice utilized by a subscriber or user of a wireless communicationservice to receive or convey data, control, voice, video, sound, gaming,or substantially any data-stream or signaling-stream. The foregoingterms are utilized interchangeably in the subject specification andrelated drawings. Likewise, the terms “access point (AP),” “basestation,” “NodeB,” “evolved Node B (eNodeB),” “home Node B (HNB),” “homeaccess point (HAP),” “cell device,” “sector,” “cell,” and the like, areutilized interchangeably in the subject application, and refer to awireless network component or appliance that serves and receives data,control, voice, video, sound, gaming, or substantially any data-streamor signaling-stream to and from a set of subscriber stations or providerenabled devices. Data and signaling streams can include packetized orframe-based flows.

Additionally, the terms “core-network”, “core”, “core carrier network”,“carrier-side”, or similar terms can refer to components of atelecommunications network that typically provides some or all ofaggregation, authentication, call control and switching, charging,service invocation, or gateways. Aggregation can refer to the highestlevel of aggregation in a service provider network wherein the nextlevel in the hierarchy under the core nodes is the distribution networksand then the edge networks. UEs do not normally connect directly to thecore networks of a large service provider but can be routed to the coreby way of a switch or radio area network. Authentication can refer todeterminations regarding whether the user requesting a service from thetelecom network is authorized to do so within this network or not. Callcontrol and switching can refer determinations related to the futurecourse of a call stream across carrier equipment based on the callsignal processing. Charging can be related to the collation andprocessing of charging data generated by various network nodes. Twocommon types of charging mechanisms found in present day networks can beprepaid charging and postpaid charging. Service invocation can occurbased on some explicit action (e.g. call transfer) or implicitly (e.g.,call waiting). It is to be noted that service “execution” may or may notbe a core network functionality as third party network/nodes may takepart in actual service execution. A gateway can be present in the corenetwork to access other networks. Gateway functionality can be dependenton the type of the interface with another network.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components (e.g., supportedthrough artificial intelligence, as through a capacity to makeinferences based on complex mathematical formalisms), that can providesimulated vision, sound recognition and so forth.

Aspects, features, or advantages of the subject matter can be exploitedin substantially any, or any, wired, broadcast, wirelesstelecommunication, radio technology or network, or combinations thereof.Non-limiting examples of such technologies or networks include Geocasttechnology; broadcast technologies (e.g., sub-Hz, ELF, VLF, LF, MF, HF,VHF, UHF, SHF, THz broadcasts, etc.); Ethernet; X.25; powerline-typenetworking (e.g., PowerLine AV Ethernet, etc.); femto-cell technology;Wi-Fi; Worldwide Interoperability for Microwave Access (WiMAX); EnhancedGeneral Packet Radio Service (Enhanced GPRS); Third GenerationPartnership Project (3GPP or 3G) Long Term Evolution (LTE); 3GPPUniversal Mobile Telecommunications System (UMTS) or 3GPP UMTS; ThirdGeneration Partnership Project 2 (3GPP2) Ultra Mobile Broadband (UMB);High Speed Packet Access (HSPA); High Speed Downlink Packet Access(HSDPA); High Speed Uplink Packet Access (HSUPA); GSM Enhanced DataRates for GSM Evolution (EDGE) Radio Access Network (RAN) or GERAN; UMTSTerrestrial Radio Access Network (UTRAN); or LTE Advanced.

What has been described above includes examples of systems and methodsillustrative of the disclosed subject matter. It is, of course, notpossible to describe every combination of components or methods herein.One of ordinary skill in the art may recognize that many furthercombinations and permutations of the disclosure are possible.Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in the detailed description, claims,appendices and drawings such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

What is claimed is:
 1. A system, comprising: a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising:determining, as function of first data representing an emergency eventassociated with a first vehicle and an aggregation of data, acommonality between the emergency event and second data received from anemergency management device; as a function of a longitude coordinateassociated with the first vehicle, a latitude coordinate associated withthe first vehicle and a defined peripheral boundary, determining acontiguous area that abuts the defined peripheral boundary; identifyinga radio access network device of a group of radio access network deviceslocated within the contiguous area; based on the commonality identifiedbetween the first data and the second data, generating metadata; andtransmitting the metadata to the first vehicle and transmitting themetadata to the radio access network device for rebroadcast, incollaboration with the group of radio access devices, to a secondvehicle in the contiguous area.
 2. The system of claim 1, wherein thefirst data comprises weather data associated with the first vehicle andthe emergency event.
 3. The system of claim 1, wherein the first datacomprises the longitude coordinate associated with the first vehicle andthe latitude coordinate associated with the first vehicle.
 4. The systemof claim 3, wherein the operations further comprise identifying anetwork device situated in a defined geographical area represented bythe longitude coordinate and the latitude coordinate.
 5. The system ofclaim 3, wherein the operations further comprise determining the definedperipheral boundary that circumscribes the longitude coordinate and thelatitude coordinate.
 6. The system of claim 5, wherein the operationsfurther comprise identifying a network device within the definedperipheral boundary.
 7. The system of claim 1, wherein the first data isreceived in response to an engine control unit associated with the firstvehicle detecting a deceleration of the first vehicle.
 8. The system ofclaim 1, wherein the first data is received in response to an enginecontrol unit associated with first the vehicle detecting a deployment ofa bag safety device of the first vehicle.
 9. A method, comprising:determining, by a system comprising a processor, an existence of acommonality between first data representing an emergency eventassociated with a vehicle and second data received from an emergencymanagement device; generating, by the system, metadata as a function ofthe existence of the commonality; based on a longitude coordinateassociated with the vehicle, a latitude coordinate associated with thevehicle, and a defined peripheral boundary, determining, by the system,an adjacent area that is contiguous with the defined peripheralboundary; identifying a grouping of radio access network devicessituated in the adjacent area; and based on the weather data,facilitating transmissions of the metadata to the vehicle and to thegrouping of radio access network devices, wherein the vehicle is a firstvehicle, and wherein the grouping of radio access network devicescollaborates to transmit the metadata to a second vehicle situated inthe adjacent area.
 10. The method of claim 9, wherein the first datacomprises weather data associated with the emergency event and the firstvehicle.
 11. The method of claim 9, wherein the first data comprises thelongitude coordinate associated with the first vehicle and the latitudecoordinate associated with the first vehicle.
 12. The method of claim11, wherein the longitude coordinate and the latitude coordinate areobtained from a global positioning satellite system device.
 13. Themethod of claim 11, further comprising identifying, by the system, anetwork device located in a defined geographical area as a function ofthe longitude coordinate and the latitude coordinate.
 14. The method ofclaim 11, further comprising determining, by the system, the definedperipheral boundary that polygonally surrounds the longitude coordinateand the latitude coordinate.
 15. The method of claim 14, furthercomprising identifying, by the system, a network device within thedefined peripheral boundary.
 16. The method of claim 9, wherein thefirst data is received in response to an engine control unit associatedwith the first vehicle detecting a change in velocity of the firstvehicle.
 17. The method of claim 9, wherein the first data is receivedin response to an engine control unit associated with the first vehicledetecting a deployment of a safety device associated with a seat belt ofthe first vehicle.
 18. A machine-readable storage medium, comprisingexecutable instructions that, when executed by a processor, facilitateperformance of operations, comprising: based on emergency event datareceived from a governmental emergency event server device and vehicledata representing an emergency event associated with a first vehicle,determining a common cross-section between the emergency event data andthe vehicle data; in response to the determining the commoncross-section, generating metadata comprising at least one of ageographical location, a time, a type of incident that has occurred, ora weather condition currently being encountered by the first vehicle; inresponse to determining a defined peripheral boundary based on alongitude coordinate associated with the first vehicle and a latitudecoordinate associated with the first vehicle, determining an area thatabuts the defined peripheral boundary; and broadcasting the metadata tothe first vehicle and broadcasting the metadata to the area based on thecommon cross-section between the emergency event data and the vehicledata, wherein the metadata to the area is broadcast to a collection ofradio access network devices that cooperate to broadcast the metadata toa second vehicle located in the area.
 19. The machine-readable storagemedium of claim 18, wherein the operations further comprise initiating asession establishment protocol to establish a session with a networkdevice of network devices associated with a radio access network. 20.The machine-readable storage medium of claim 19, wherein the latitudecoordinate is a first latitude coordinate, the longitude coordinate is afirst longitude coordinate, and the defined peripheral boundary is afirst peripheral boundary, and wherein the operations further comprise,as a function of a second longitude coordinate associated with thenetwork device and a second latitude coordinate associated with thenetwork device, determining a second defined peripheral boundary thatencloses the network device.